-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Python CPU test - basic scenario #4
Conversation
while time() < end: | ||
a() | ||
b() | ||
print(x) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assume this is needed to avoid the compiler optimizing away the writes to x?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, locals would be optimized without a usage in more recent python versions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might want to add a comment explaining this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Its nice to have a test for this. I had a minor ⛏️ about commenting the need for the print(x)
but otherwise LGTM.
Description
When moving to the docker implementation of tests, we removed the python test.
This adds it back in.
Naming adjustment: ensure we explicitly have the unit in the EXECUTION_TIME_SEC variable.